Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1102

reference
16-tree-1
name
1102
tree-preservation-order

undefined

16-tpo-1
uprn
address-text
point
POINT (-1.010639 50.888321)
geometry
MULTIPOLYGON (((-1.010582 50.888315,-1.010585 50.888326,-1.010593 50.888337,-1.010605 50.888345,-1.010621 50.888350,-1.010638 50.888352,-1.010656 50.888350,-1.010672 50.888345,-1.010685 50.888337,-1.010693 50.888327,-1.010696 50.888316,-1.010693 50.888305,-1.010686 50.888295,-1.010673 50.888287,-1.010657 50.888282,-1.010640 50.888280,-1.010622 50.888281,-1.010606 50.888286,-1.010594 50.888294,-1.010585 50.888304,-1.010582 50.888315)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL